4 Device Settings and Properties > 4.2 Settings Stored in the Windows Registry

4.2
The WinMux2k driver parameters are located in the registry path
HKLM\System\CurrentControlSet\Enum\Root\winmux\000X\Device Parameters.
X is the number of the device instance.
All values listed below will be created during the installation of the WinMux2k driver. The set­tings are provided by the winmux2k.inf file. If you want to write your own preferences to the Registry you can edit the inf file before installing the driver.
Table 6:
AT
AT&S0
AT\Q3
AT+ICF=3
AT+CMUX=0
This multi-string value contains several AT commands which are used to switch the module to multiplexer mode. Possible ERROR codes resulting from unsupported com­mands are ignored by the WinMux2k initialization sequence.
Timeout value used only during the initialization of the mod­ule. 2000 is the maximum number of milliseconds the mod­ule can take to respond to AT requests.
Name of the first virtual port. Each virtual port must have a unique name. Otherwise the driver will fail to start up.
Number of Virtual Channels visible as COM ports. The WinMux2k driver supports up to 3 virtual ports. The number of VirtualChannels must be less or equal to TotalChannels.
If the number of TotalChannels is greater than VirtualChan­nels and no VirtPortX value for additional channels is defined, these additional ports are not visible as COM ports. They can be accessed by the link named SERMUX_CONTROL_PREFIX defined in sermux_i.h. This allows to hide virtual ports to the user. Each physical port can have one hidden port.
Timeout during module initialization. The timeout takes effect only when the driver tries to restart the module from Power Down or to wake it up from SLEEP mode AT+CFUN=0. The time is given in milliseconds.
This virtual channel is used to send the power down com­mands to the module. The data state on this channel may be disturbed during power down and cannot be reconstructed by the driver.
0 Default for XC18
The driver does not try to reconnect to the module if DSR changes. This feature can be switched off if an application controls the DSR line with AT&S.
1 Default for all modules except XC18
The driver tries to reconnect to the module if DSR changes. The driver can detect if the module was disconnected and reinitializes it before the first data errors occur.
ClosePort
(not applicable to TC45 and XC18)
AT+IPR=0
AT^SMSO
ClosePort
(TC45, XC18 only)
The command AT+CFUN=0 has been chosen as factory default for compatibility with older Siemens products. If you prefer to use one of the more efficient CYCLIC SLEEP modes it can be replaced with AT+CFUN=5 or 6 or 7 or 8 or 9. See [3] and [4] to verify the SLEEP mode types supported by your product. To avoid editing the Windows Registry you can alter the corresponding parameter in the winmux2k.inf file and then reinstall the driver.
AT+IPR=0
AT^SMSO
0 Default for TC45 and XC18
The driver does not wait for the DSR signal to go low when the module is shut down. Instead, the parameter Recover­Time (see below) is used.
1 Default for all modules except TC45 and XC18
The driver waits for the DSR signal to go low when the mod­ule is shut down. In this case the parameter RecoverTime is not used. If the module is not switched off with the AT com­mands defined in the parameter ClosePort this parameter must be set to 0.
From version 3 onwards, the Multiplexer Protocol supports power saving control with a special multiplex control frame. This provides the possibility of sending power down com­mands to the module without accessing any data channel.
If the connected module only supports the Multiplexer Pro­tocol version 2 this value is not used. If the supported Multi­plexer Protocol version is 3 or higher, the multiplex power control is used instead of the values “PowerCmdPort” and “PowerDown”. In this case this value corresponds to the power down command of the multiplex power down frame described in [5]. If the value is greater than 255 there is no power down frame sent for Multiplexer Protocol 3.
This registry value provides the possibility to force the driver to use a lower multiplex protocol version than the maximum supported. The multiplex protocol has been improved con­tinuously by adding several features. The multiplex protocol version is negotiated with the connected module during mul­tiplex startup. It is used to ensure compatibility between dif­ferent multiplex driver and module generations. The registry value isn’t mandatory, by default the WinMux driver uses always the latest protocol implementation with all available features. If for some reason an older multiplex protocol shall be used it can be controlled with that registry value. For fur­ther information about the multiplex protocol versions refer to the “Multiplexer User’s Guide”.
Modules with multiplex protocol version 4 and above use a kind of HDLC framing to secure the data transmission on the virtual ports and avoid data loss at high transfer rates and much data traffic. This registry value provides the possibility to adjust the size of the HDLC window which defines the maximal number of outstanding HDLC packets. It can be between 2 and 7.
This Registry value is not mandatory. If it is not added to the Registry the value 4 will be assumed by default. Please note that the value is negotiated with the module.
The following Registry values in the path
HKLM \System\CurrentControlSet\Services\winmux2k\Parameters
are used to configure the TRACE outputs. These values are only valid for the debug version of the device driver.
The next masks are only for driver checks and represent internal variables and states of the serial Multiplexer Device driver.